Reading device with shortcut read function

ABSTRACT

In some embodiments, a reading device is provided with a shortcut read mode in which a user can instruct the reading device of the type of document (e.g., invoice, package label, newspaper, etc.) that is to be read so that the device can more efficiently find and read back to the user desired (target) information from the document.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to and claims the benefit under 35 U.S.C.120 and 121 of allowed U.S. application Ser. No. 11/967,929, filed onDec. 31, 2007, and issued as U.S. Pat. No. 8,185,398 on May 22, 2012 theentire contents of which is incorporated herein by reference.

BACKGROUND

The embodiments of the invention relate to a reading machine forimpaired persons such as individuals who are visually impaired or havedyslexia.

People with disabilities, such as impaired vision or dyslexia, may havedifficulty reading printed material. Automatic systems are needed torender documents as audio recordings.

It is known to provide a mobile print digitizer for the visuallyimpaired. One known device captures printed documents and reads them tothe user. A camera or scanner captures an image of a printed page, andthen runs optical character recognition (OCR) on the image. The outputis fed to a speech synthesizer such as a text-to-speech (TTS) system.Unfortunately, existing systems can be inefficient in their ability toallow a user to efficiently navigate a document as the reader reads itto the user. Accordingly, new approaches are desired.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings inwhich like reference numerals refer to similar elements.

FIG. 1 is a diagram of a reading apparatus in accordance with someembodiments.

FIG. 2 is a flow diagram of a routine for implementing a shortcut readprocess in accordance with some embodiments.

FIG. 3 is a diagram generally showing an outline of a shortcut templatein accordance with some embodiments.

FIG. 4 is an example of a food package document portion showingidentified fields.

FIG. 5 is an example of an invoice document portion showing identifiedfields.

FIG. 6 is a flow diagram of another routine for implementing a shortcutread process in accordance with some embodiments.

DETAILED DESCRIPTION

One of the challenges for reading device users is that with some typesof text-containing documents, the user may only be interested in readinga portion of the text. Accordingly, with some embodiments, a readingdevice is provided with a shortcut read mode in which a user caninstruct the reading device of the type of document (e.g., invoice,package label, newspaper, etc.) that is to be read so that the devicecan more efficiently find and read back to the user desired (target)information from the document.

FIG. 1 shows a block diagram of a reading apparatus 102 to read to auser a document 101 to be scanned in accordance with some embodiments.Reader 102 generally comprises a processor 104, user interface 106,camera 108, memory 110, and auditory output device 112, coupled togetheras shown.

The camera may comprise any suitable device such as a charge coupleddevice (CCD) camera to acquire a raster image of the text document 101,as is known in the art. It may scan a document line by line, section bysection or it may image an entire page or sheet at once. Similarly, thedocument can comprise any material with visual text to be read. Thisincludes, for example, a page, sheet, package surface, slip of paper (aswith some receipts), a video screen (e.g., at an airport), or the like.

The auditory device 112 could comprise any suitable device to auditorilyconvey the read text to the user. For example, it could comprise one ormore speakers and/or audio interface ports for connection to headphonesor the like.

The user interface 106 may constitute any suitable components, known ornot yet developed, to allow a user to conveniently control the reader.For example, the user interface could comprise one or more buttons,wheels, joysticks or other input control components that allow a user tomanually control the reader without necessarily being able to see theuser interface (i.e. it should allow a user to control at least some ofthe components with the appropriate feedback mechanism). In someembodiments, the user interface includes a five button interface, suchas that shown in FIG. 1, with up (“U”), down (“D”), left (“L”), right(“R”), and select (“S”) buttons, to allow a user to convenientlynavigate through a document, as addressed more below.

In the depicted embodiment, through auditory device 112, an auditorymenu 113 is provided to allow a user to select, among other things, aread shortcut function. A portion of the auditory menu is showngraphically for illustrative purposes but may not be actually visuallypresented on a device. That is, the user may press a button (e.g., theselect button) to have one or more menu options read and select anoption or go “down” further (e.g., via a down button) into an option inresponse to the options being read to the user. (The reading device 102may or may not include a video screen or other visual output component,e.g., as part of its user interface. On the other hand, in someembodiments, a screen such as a liquid crystal display (LCD) screen maybe provided for visual control and/or for document magnification (e.g.,for users having at least some vision).

The user interface could also include input ports (which may alsofunction as output ports) such as universal serial bus (USB), so-called“Firewire”, and/or wireless ports, e.g., to allow a user to import anelectronic document that may or may not be in a text format. Forexample, portable document format (PDF) documents (or the like) could beimported for auditory reading to a user. In addition, the user interfacecould include speech-to-text capability, e.g., a microphone withsuitable speech-to-text engine. Of course, as with any feature,especially those requiring substantial hardware and/or processing,trade-offs must be made between cost, power consumption, operatingefficiency, performance accuracy, and feature capability.

The processor and memory may comprise any suitable combination of memoryand processing circuits, components, or combinations of the same toexecute routines to control the reader 102. The memory 110 comprisesdevice control (DC) software code 111 to control the reader 102 andexecute its various functions. In the depicted embodiment, the devicecontrol code has at least several modules including an optical characterrecognition (OCR) module, a read shortcut (RS) module, and atext-to-speech (TTS) module. The OCR module further includes acharacterization (CZN) module, and the read shortcut module includes oneor more templates 117 and target filters 119 for the different documenttypes having read shortcut options in the reader 102. There may be moremodules and in some embodiments, the modules may not necessarily berelated to each other as shown.

The device control code controls scanning (digitized documentacquisition), reading navigation, and general system functionality. TheOCR module converts the pre-text (e.g., rasterized scanned image)document into text data and characterizes it, using the characterizationmodule, so that it may be read to a user. (As used herein, “reading”means to convey or provide text in an audio form to a user.)

The read shortcut module (e.g., in response to a read shortcut operationbeing selected by a user) processes the document based on properties andrules defined in a template associated with that document type to“efficiently” read to the user one or more specific targets from thedocument. In the depicted embodiment, the document types correspond tothe different shortcut templates 117 shown within the RS module. Thatis, a separate template may be used to identify text fields, expected inthe document type selected. A filter is then used to identify desiredtarget information from the text fields for reading to the user.

There may be many different types of documents for which read shortcutcapability may be desired. For example, sub-menu 115 shows document typeoptions including medical labels, restaurant menus, bills/receipts, foodpackage labels, currency, and custom types. Others may also be includedsuch as larger document types such as newspapers, magazines, and thelike.

The templates and/or filters may be predefined and provided as part of areading device to a customer. In addition, provisions can be made sothat users can create and/or modify templates and/or filters (or acquirethem from elsewhere) for different desired document types or so they cancontrol or change how a read shortcut for a document type is to occur(e.g., what targets to look for and/or how to read them). For example, auser might generate a template for a London bus schedule. Tools could bemade for users to more conveniently create such custom templates. Forexample, software could be provided for a user's personal computer tocreate custom templates and/or filters from scanned documents.

FIG. 2 generally shows a routine for implementing a read shortcutroutine, e.g., from the RS module of FIG. 1, in accordance with someembodiments. In some embodiments, conventional OCR and TTS modules maybe used in cooperation with a CZN module designed, among other things,to perform methods and concepts discussed herein. (This comprisesdeveloping an OCR with a suitable characterization capability,appropriately modifying and/or configuring an “off-the-shelf” OCRprogram to have suitable characterization, or another feasibleapproach.)

Upon initiation of a read shortcut option at 202, the reader receives(e.g., by eliciting) a document type option for the read shortcutfunction. With the exemplary user interface of FIG. 1, this couldcorrespond to a user selecting a “shortcut” option and then selecting aparticular document type. In some embodiments, the user could go furtherand select a particular sub option for a given document type. Forexample, with a given document type, different targets or readingoptions may be desired.

At 204, the reader (or reading device) initiates document acquisition.The text-containing document may be acquired in various different ways.It could be done through the importation of an electronic document or byscanning a document such as text-containing document 101 using thecamera 108. Regardless of how it is acquired, the digitized documentfile should be in a suitable form for the utilized OCR module. Forexample, many OCR packages typically accept raster image formatscommonly found throughout the document management industry such as TIF,BMP, PCX and DCX, to mention just a few. Depending upon particulardesign considerations, a suitable OCR solution could also be made toaccept input from other sources such as fax input formats, PDF (orsimilar) formats, or common scanner driver formats such as TWAIN andISIS.

At 206, text from the acquired document is characterized, based on thetemplate for the selected document type, to identify and characterizefields, as defined in the template. This involves OCR'ing the digitizeddocument to identify text and organizing it into fields that are definedin the template. (More on templates will be presented below.) Anysuitable OCR tool (or module), presently available or specificallydeveloped, capable of suitably identifying text layout and formatattributes may be employed. Currently available OCR tools are generallyflexible enough to conform to needed performance for techniquesdiscussed herein.

OCR modules generally perform text recognition by defining an areawithin a frame to be converted and then processing it and examining theresults. They typically define vector bounding boxes around blocks orsections of text such as individual characters, sentences, lines,paragraphs, etc. The bounding boxes identify text block layout and canalso be used to identify format attributes such as font size and thelike. For example, when a bounding box indicates the dimensions of acharacter, its font attributes or even style attributes can bedetermined directly using the character dimensions, character imagemapping, character-to-area ratios, or the like. Other well-known methodscan also be used for the OCR module to recognize text format attributes.

OCR programs are usually fairly flexible in allowing designers to adjustsoftware imaging attributes. Varying image attributes may enhance themanner in which the OCR software views text. For example, lowering thesoftware, or display, resolution (e.g., not the scanned resolution) mayallow the software to “see” a clearer image of the text thus improvingthe initial chances of correct recognition. Configuration settings mayalso be varied based on given design considerations. They can affect theformat characteristics of what is being read such as text style (e.g.,plain, italic, numeric, image), text size, and font type.

Most OCR software allows the user to set margins of acceptable errorwhen attempting to recognize a text image. Similarly, confidence levelsfor recognition depending on results of first iterations may be used andadjusted depending upon design considerations. Confidence levels aremeasures of certainty. Depending upon desired operating performance,different (e.g., two or more) different confidence levels could be used.

Error detection methodologies are also commonly employed. For example,error detection tools include spell checks and automatic correctionsbased on the software or user specific dictionaries. Various propertiessuch as uppercase words, numeric expressions, roman numerals, propernouns, math functions, abbreviation and acronyms may also be comparedagainst appropriate more-particular dictionaries. Resolution of patternsinvolving text and numerals may be varied according to ambiguitiesdominant in the patterns.

Depending on what type of OCR module is used, the identified textcharacters may or may not be grouped logically into meaningful blocksfor reading to a user. Therefore, a characterization module can be usedto further organize the OCR'd text blocks into groups (or blocks) suchas sentences, paragraphs, sections, or the like. As discussed morebelow, the template for the selected document type defines one or morefields, and the text is organized into these fields so that desiredtarget information can be more readily identified and read to a user.Characterization can also be used to link different blocks with oneanother and to assign hierarchal and other reading-flow attributes tothe OCR'd text. For more on characterization, reference may be made toco-pending, commonly owned U.S. patent application entitled: “READINGDEVICE WITH HIERARCHAL NAVIGATION,” which is hereby incorporated byreference into this application.

In some schemes, depending on attributes and/or attributes defined inthe template, the reading device may start scanning (either optically orwithin the software) at a higher level, i.e., lower resolution to morequickly identify information specified in the template for the field(s)defined in the template. If no (or an insufficient amount) of pertinentinformation is found, it may increase scan resolution to increase thechance of finding such information. Likewise, when pertinent informationis found, it may also increase resolution, if deemed appropriate by thetemplate, to acquire better information in a region that is close toand/or encompassing the found information.

From here, it may perform specified heuristics to confirm that thefield(s) identify the sought after target information and to collect anyother needed information associated with the target(s). It may alsoinitiate further OCR'ing and/or characterization, especially oninformation associated with the target, so that it can efficiently beread to the user.

At 207, the routine determines (or confirms) if one or more fields forthe selected template were matched (or identified). If not, it proceedsto 209 and notifies the user that no matches were found, and the routineends. On the other hand, if it is confirmed at 207 that one or moretemplate fields were in fact identified, then it proceeds from there to208.

At 208, the characterized fields are filtered to identify informationfor one or more targets, defined in a filter, for reading to a user. Insome embodiments, this could be done after field characterization hasoccurred, or it could be done concurrently with field characterization,depending on particular design considerations. The filtering can occurin any suitable manner and the “filters” may be generated or defined inany suitable way, as well. For example, they could be provided asseparate files, loaded into the device and selected upon selection of adocument type. Alternatively, they could correspond to input from a userthrough the user interface. For example, the user could select target(s)from target options presented to the user. A user could also make oracquire its own customized filter, e.g., in file form. In addition, morethan one filter could be available for each document type.

At 210, the reading device reads the target information, passed throughthe filter, to the user. To do this, any suitable text-to-speech (TTS)solution may be used. In some embodiments, the user may be allowed tonavigate through the text sequentially or in some other desired way.

FIG. 3 shows an exemplary form for a shortcut template 302 to be used bya read shortcut module, as discussed above to generate text fields,defined by the template, for the document type. The template includesone or more fields 303 (303 ₁ to 303 _(N)) and a template rules section305 applicable to the whole template. Each field corresponds to a groupof information, having one or more desired targets, that is expected tobe in the document type. Through its fields and general rules section, atemplate describes attributes associated with the different fields thatare expected in the document type. For example, for each field, it maydescribe text box layout and the text box properties that the processor,through characterization discussed previously, is attempting to matchagainst the acquired document to be able to extract some specific“target” information therefrom, e.g. the total amount of a bill for aninvoice type document. Field (or text box) properties may include, butare not limited to (1) layout properties (e.g. relative location of textbounding boxes of a nutrition fact label (for a food package document),i.e. upper left corner, or below code bar), (2) content properties(e.g., some specific text such as “nutrition facts” or “total”, or animage such as a logo or a bar code), (3) style properties (e.g. aparticular font style and size of a title), (4) content type properties(e.g. if a text box contains a number, a proper name, etc), and (5)target properties, which indicate that this text box contains the textto read as a shortcut.

The matching process (block 206 in FIG. 2) compares the template withthe input document and calculates matching scores for different sectionsagainst the fields defined in the template. This may not be an exactprocess. If a score for a candidate field section is higher than apredefined threshold for that field, then it is deemed a match, and thetext in the section (text box) is identified as such.

The output from this matching (or characterization) process may be asequence of text prompts to be read along eventually with the contenttype, e.g. “the total is 25 dollars”. Here “total” and “dollar” arecontent type properties which are read in order to make the output asclear as possible. From here, as discussed above, target informationidentified in a filter is extracted from the characterized text fieldsand read to the user.

FIG. 4 shows an exemplary food package label that could be scanned forshortcut reading using the reader of FIG. 1. With this example, assumethat the RS module includes a food label template that defines severaldifferent fields including “nutritional information” and “preparationinstructions” fields. After characterization using the food packagetemplate, the processor might identify the nutritional information andbound it using box 402. It would be characterized and identified as anutritional information field. Likewise, using the preparationsinstructions field attributes in the template, it might identify theinformation in box 404 as this field. As with the nutritionalinformation field, it would characterize it so that targets could beextracted and properly be read to a user by way of a filter for the foodpackage document type.

FIG. 5 shows another example, this time an invoice. With this example,assume that, among other things, the template for bills/invoicesincludes “total amount” and “itemized debits” fields. Using the fieldattributes, the processor might define the text in 502 and 504 as “totalamount” fields and the text in 506 as “itemized debits” fields. In doingthis, it might use content properties such as words like: “total”,“amount owed”, “$”, “net”, and the like. The rules and/or specifiedproperties could cause the reader (processor) to find one or more ofthese terms and then confirm, based on specified criterion in thetemplate, that a money amount format (e.g., “X.XX”) is found in anacceptable position relative to the found key term(s). It, for example,might also perform comparison and/or arithmetic logic to confirm that itis larger than a sum from the “itemized debits” field. In this example,it found two total amount fields, 502 and 504. It might identify one ofthem, based on a higher probability score, and then prepare that one forreading to a user.

FIG. 6 shows a flow diagram for a read shortcut routine in accordancewith some alternative embodiments. With this routine, the user is notrequired to select a particular document type, but rather, the readingdevice attempts to find a matching template from a plurality ofavailable templates. At 602, a read shortcut operation is initiated.This could correspond to a user simply pressing a read shortcut (orequivalent) button.

At 604, a digitized document to be read is acquired. Next, at 606, thedevice selects a next template. If it is the first time through, thenext template is the first template from the plurality of availabletemplates. At 607, it characterizes the document to determine if it is amatch for the selected template. For example, match thresholds could bepre-specified, and the reading device could determine if one or moreidentified fields, either separately or added together, satisfy thethreshold to constitute a match.

If it determines that the selected template was not a match, then itproceeds to 609 and determines if there is a “next” template. If so, itloops back to 606 and continues as described. If, however, at 609, itwas determined that there are no more templates, then from there, itgoes to 611 and notifies the user that no matches were found.

Returning back to 608, if it was determined that the selected templateis in fact a match for the acquired document, then it proceeds to 610 tofilter the document and extract target information from the document.From there, it proceeds to 612 and reads the target information to theuser.

In the preceding description, numerous specific details have been setforth. However, it is understood that embodiments of the invention maybe practiced without these specific details. In other instances,well-known circuits, structures and techniques may have not been shownin detail in order not to obscure an understanding of the description.With this in mind, references to “one embodiment”, “an embodiment”,“example embodiment”, “various embodiments”, etc., indicate that theembodiment(s) of the invention so described may include particularfeatures, structures, or characteristics, but not every embodimentnecessarily includes the particular features, structures, orcharacteristics. Further, some embodiments may have some, all, or noneof the features described for other embodiments.

The invention is not limited to the embodiments described, but can bepracticed with modification and alteration within the spirit and scopeof the appended claims.

It should be appreciated that example sizes/models/values/ranges mayhave been given, although the present invention is not limited to thesame. As manufacturing techniques (e.g., photolithography) mature overtime, it is expected that devices of smaller size could be manufactured.Further, arrangements may be shown in block diagram form in order toavoid obscuring the invention, and also in view of the fact thatspecifics with respect to implementation of such block diagramarrangements are highly dependent upon the platform within which thepresent invention is to be implemented, i.e., such specifics should bewell within purview of one skilled in the art. Where specific details(e.g., circuits) are set forth in order to describe example embodimentsof the invention, it should be apparent to one skilled in the art thatthe invention can be practiced without, or with variation of, thesespecific details. The description is thus to be regarded as illustrativeinstead of limiting.

What is claimed is:
 1. An apparatus, comprising: an acquisition deviceconfigured to acquire a digitization of at least a portion of adocument; and at least one processor configured to identify targetinformation in the at least a portion of the document, wherein theacquisition device is configured to increase a scan resolution based onan amount of information identified in the acquired digitization of theat least a portion of the document.
 2. The apparatus of claim 1, whereinthe acquisition device is a camera.
 3. The apparatus of claim 1, whereinthe at least one processor is configured to execute, in response to theuser selecting a particular type of document, a filter to identify thetarget information.
 4. The apparatus of claim 3, wherein the at leastone processor is configured to characterize text in the document basedon an associated template.
 5. The apparatus of claim 1, wherein thetarget information is associated with one of a plurality of documenttypes.
 6. The apparatus of claim 5, wherein the at least one processoris configured to receive additional document type options from the user.7. The apparatus of claim 1, wherein the at least one processor isconfigured to cause the target information to be outputted to the userwithout outputting to the user other text from the acquired documentportion.
 8. The apparatus of claim 1, comprising at least one speaker,wherein the at least one processor is configured to cause the at leastone speaker to output auditory document type options, and wherein the atleast one processor is configured to receive the user's dictatedselection of one of the document type options.
 9. The apparatus of claim1, in which the target information is made available for reading to theuser more quickly than if the whole document portion was made availablefor reading to the user.
 10. A method, comprising: receiving, from aportable reading device, a user's selection of a document type frommultiple document types; acquiring a digital file for at least a portionof a document of the selected document type; performing opticalcharacter recognition (OCR) on the digital file; extracting targetinformation from the digital file after the OCR of the digital file hasbeen performed, wherein the acquiring the digital file comprisesscanning the at least a portion of the document with a first scanresolution and scanning the at least a portion of the document with asecond scan resolution, wherein the second scan resolution is higherthan the first scan resolution.
 11. The method of claim 10, wherein theacquiring includes imaging the at least a portion of the document with acamera that is part of the portable reading device.
 12. The method ofclaim 10, comprising searching for one or more key terms associated withthe target information.
 13. The method of claim 12, wherein the one ormore key terms are searched as the optical character recognition isbeing performed.
 14. The method of claim 10, wherein each of themultiple document types is defined by a template executable in theportable reading device.
 15. The method of claim 10, wherein themultiple document types include an invoice document type.
 16. The methodof claim 10, comprising receiving from the user a document typedefinition.
 17. The method of claim 10, further comprising outputting atleast some of the target information in an auditory form.
 18. A method,comprising: receiving a selection of document type; acquiring a digitalfile for at least a portion of a document, the document having theselected document type; performing optical character recognition (OCR)on the digital file; characterizing text outputted by the OCRperformance into one or more fields, the characterizing based on one ormore templates; extracting target information from the one or morefields; and outputting the target information, wherein the one or moretemplates define the one or more fields of the selected document type,the definition including one or more content properties of the one ormore fields, one or more style properties of the one or more fields, oneor more content type properties of the one or more fields, one or moretarget properties of the one or more fields, or any combination thereof.